If typically more rows are accessed sequentially ( maybe the table is clustered), then the larger page size is more efficient. 如果通常是顺序访问大量行(该表可能进行了群集),那么比较大的页大小会更有效。
If DB2 understands that two rows clustered together are on the same page, requests for both of them might result in a single I/ O if the requests are close together in time. 如果DB2知道聚集在一起的两行是在同一页上,那么如果请求在时间上紧邻的话,对于这两行的请求就会产生一个I/O。
Intent share locks on all clustered index pages containing those rows, unless the page is already protected by an IX lock. 包含那些行的所有聚集索引页上的意向共享锁,除非页已被ix锁保护。